docs: Adds documentation for the 112 exit code when posix-compliant exit codes are enabled.
#6294
+27
−70
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
cypress-documentation
|
||||||||||||||||||||||||||||||||||||||||
| Project |
cypress-documentation
|
| Branch Review |
docs/exit-112-network-err
|
| Run status |
|
| Run duration | 04m 36s |
| Commit |
|
| Committer | Cacie Prins |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
0
|
Skipped
|
0
|
Passing
|
310
|
| View all changes introduced in this branch ↗︎ | |
UI Coverage
10.75%
|
|
|---|---|
|
Untested elements
|
2518
|
|
Tested elements
|
3
|
Accessibility
97.21%
|
|
|---|---|
|
Failed rules
|
1 critical
3 serious
4 moderate
0 minor
|
|
Failed elements
|
28
|
cacieprins
force-pushed
the
docs/exit-112-network-err
branch
from
e934209 to
2b0bd11
Compare
MikeMcC399
reviewed
Oct 9, 2025
Comment on lines
+15
to
+17
| **Features:** | ||
|
|
||
| - When the `run` command requires successful negotiation with the Cypress Cloud API and the `--posix-exit-codes` flag is set, Cypress will now exit with code `112` when it cannot determine which spec to run next due to network conditions. These Cloud API negotiations are required when either `--record` or `--parallel` flags are set. Addresses [#32485](https://github.com/cypress-io/cypress/issues/32485). Addressed in [#32635](https://github.com/cypress-io/cypress/pull/32635). |
There was a problem hiding this comment.
The text should probably come out of PR cypress-io/cypress#32635 otherwise it is unclear where the definitive text for the release notes is supposed to be reviewed.
MikeMcC399
reviewed
Oct 9, 2025
| | [4.9.0](/app/references/changelog) | Added `--quiet` flag to `cypress run` | | ||
| | Version | Changes | | ||
| | ------------------------------------------ | -------------------------------------------------------------------------------------------------------- | | ||
| | [15.5.0](/app/references/changelog#15-5-0) | Modified exit code documentations from narrative to a reference table, adding the 112 exit code scenario | |
There was a problem hiding this comment.
Generally the history table is used to document the changes to Cypress, rather than the changes to the documentation. So here the change would be something like
"Added POSIX exit code 112 for Cypress Cloud network failure"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated documentation for cypress-io/cypress#32635.
This converts the existing narrative-based documentation of Cypress' exit codes to a more comprehensive reference table, comparing both default and POSIX behavior in different scenarios. It also adds references to the
112exit code that will be used when a--recordor--parallelrun cannot communicate with the Cypress Cloud API due to network level errors.